6. Planning Mailbox Moves and Coexistence
To move mailboxes from Exchange
Server 2007 to Exchange Server 2010, the Exchange Server 2007 Mailbox
server must be running Exchange Server 2007 SP2. As explained in detail
in the Section 6.5 section of this article, mailboxes are moved to Exchange Server 2010 using Move Requests
through the Exchange Server 2010 EMC or EMS. However, when moving
mailboxes from Exchange Server 2007 to Exchange Server 2010 these move
processes are performed online, meaning end users can access their
mailboxes during the move. This is different behavior than when moving
mailboxes from Exchange Server 2003, where users are unable to access
their mailboxes during the move.
7. Planning Continuous Replication Migration
The Exchange Server 2007
high-availability solutions for mailboxes have been replaced in Exchange
Server 2010 with a single high-availability model: database mobility.
Database mobility is composed of database availability groups and
database copies.
In a nutshell, database mobility has the following characteristics:
Is a combination of database availability groups and database copies
Abstracts databases from Exchange Server 2010 Mailbox servers; databases are now managed at the organization level
Provides high availability and site resilience
Provides 30-second switchover/failover with simplified administrative experience compared to Exchange Server 2007
Allows for more storage choices, such as Serial ATA (SATA) disks and JBOD (Just a Bunch of Disks) configurations
In combination with other features, makes deployments without database backups possible
Replaces
Standby Continuous Replication (SCR), Local Continuous Replication
(LCR), Single Copy Cluster (SCC), and Cluster Continuous Replication
(CCR) from Exchange Server 2007
The Exchange Server 2007 mailbox high-availability concepts do not exist in Exchange Server 2010; mailbox high-availability migration
consists of creating DAGs and database copies in Exchange Server 2010
and moving mailboxes from Exchange Server 2007 to Exchange Server 2010.
8. Planning Unified Messaging Migration
We will cover the migration of UM from Exchange Server 2007 to Exchange
Server 2010. Typically, Exchange Server 2010 UM servers are deployed
after the Exchange Server 2010 Client Access and Hub Transport servers
but before Exchange Server 2010 mailboxes are implemented.
UM is migrated from Exchange Server 2007 as follows:
Verify
that you have deployed the Exchange Server 2010 Client Access, Mailbox,
and Hub Transport server roles in your organization.
Install Exchange Server 2007 SP2 on all existing Exchange Server 2007 UM servers in your organization.
Install the Exchange Server 2010 UM server role, including any required language packs.
If
you will have Exchange Server 2007 UM servers and UM-enabled mailboxes
on Exchange Server 2007 in your Exchange Server 2010 organization, you
need additional dial plans and UM hunt groups with new pilot numbers.
If you're integrating with Office Communications Server (OCS) 2007, you will need to create a new UM Session Initiation Protocol (SIP) Uniform
Resource Identifier (URI) dial plan configured with a new pilot
identifier. You then have to disable Unified Messaging for your users
and then re-enable these users with the new SIP URI dial plan.
Note:
A
separate dial plan is required if you are using versions of OCS prior to
OCS 2007 R2 with Cumulative Update (CU) 5. OSC 2007 and OCS 2007 R2 do
not distinguish between Exchange Server 2007 and Exchange Server 2010 UM
servers, and round-robin all calls across both Exchange Server 2007 and
Exchange Server 2010 UM servers regardless of the version of the
recipient's mailbox. OCS 2007 R2 CU5 is version-aware, so if CU5 is
deployed an additional dial plan is not required.
Add the Exchange Server 2010 UM servers to the Exchange Server 2007 UM dial plan.
Import to Exchange Server 2010 UM any custom prompts created for Exchange Server 2007 auto attendants or UM dial plans.
Send incoming calls to the Exchange Server 2010 UM servers by configuring all IP gateways or IP PBXs.
Exchange Server 2010 UM determines if the call is for an Exchange
Server 2007 or Exchange Server 2010 mailbox and routes the call
accordingly. If the call is for an Exchange Server 2007 mailbox,
Exchange Server 2010 UM routes the call to an Exchange Server 2007 UM
server in the same dial plan using round robin.
Move Exchange Server 2007 UM-enabled mailboxes to Exchange Server 2010.
After
all Exchange Server 2007 UM-enabled mailboxes have been moved to
Exchange Server 2010, remove the Exchange Server 2007 UM servers from
the UM dial plan.
Remove the Exchange Server 2007 UM servers from the environment.
9. Removing Exchange Server 2007 Computers
Removing the last server
running Exchange Server 2007 from your Exchange Server 2010
organization has some similarities to removing Exchange Server 2003. The
removal is done by following these steps:
To
uninstall the last Exchange Server 2007 computer you require Exchange
Organization Administrator permissions in Exchange Server 2007, as well
as the Organization Management role in Exchange Server 2010.
Confirm that all legacy Exchange features are decommissioned or replaced.
Confirm that all mailboxes and public folders are migrated to Exchange Server 2010.
Ensure that all OABs have been moved to Exchange Server 2010.
Verify
that Send and Receive connectors have been created and configured on
Exchange Server 2010, and inbound and outbound Internet SMTP traffic has
been moved to Exchange Server 2010. Also verify that your DNS
MX records have been modified to resolve to Exchange Server 2010 Edge
Transport or Hub Transport servers, and verify in Exchange Server 2010
that no Exchange Server 2007 computers are listed as smart hosts for any
Send connectors.
Check
internal and external DNS records to verify that the following protocol
services are resolving to Exchange Server 2010 Client Access servers.
(Confirm as well that all clients are using Exchange Server 2010 for
these services and protocols.)
Remove public folder stores from Exchange Server 2007 by using the EMC.
Uninstall Exchange Server 2007 from the last server.
